Recreational vehicle interactive telemetry, mapping, and trip planning system

ABSTRACT

An interactive system for use in connection with recreational vehicle usage includes a server system, including an off-road trail database containing trail data, trail condition information, and points-of-interest information, as well as a trip mapping system accessible by any of a plurality of riders, allowing a rider to create a route based on the data in the off-road trip database. The server system further includes a trail maintenance interface accessible by users affiliated with an authorized group to edit the trail data, trail condition information, and points-of-interest information associated with the authorized group. The server system includes a location data management system configured to receive location data, allowing a rider to publish location information to one or more other riders, and a user feedback interface configured to receive trip data from riders for publication, including information describing an actual route and user data associated with that route.

CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional of U.S. patent application Ser. No.14/190,369, filed on Feb. 26, 2014 (Attorney Docket No.PLR-15-25635.03P-US-e), and entitled “RECREATIONAL VEHICLE INTERACTIVE,TELEMETRY, MAPPING, AND TRIP PLANNING SYSTEM,” which claims the benefitof U.S. Provisional Patent Application Ser. No. 61/769,378, filed onFeb. 26, 2013 (Attorney Docket No. PLR-00TC-25635-01P-US-e), andentitled “RECREATIONAL VEHICLE INTERACTIVE, TELEMETRY, MAPPING, AND TRIPPLANNING SYSTEM,” the complete disclosures of which are expresslyincorporated herein by reference.

BACKGROUND AND SUMMARY

Recreational vehicles, such as motorcycles, or off-road vehicles such asall-terrain vehicles (ATVs) and snowmobiles, are widely used forrecreational purposes. These vehicles might be used on both roads andtrails, or only on trails. The trails often pass over a mixture ofprivate and public properties, which can extend for hundreds of miles inmany directions, and through different areas. Such trails generallyextend through rural areas, but can connect to gas stations,restaurants, bars, maintenance locations, scenic areas, and other pointsof potential interest to outdoor adventurers.

Currently, clubs in areas where such trails exist maintain the trails onwhich such off-road vehicles are used. For example, a snowmobile club ina particular geographical area will maintain a relationship with theowners of the lands through which the trails pass, and will monitor andmaintain the trail conditions (e.g., by monitoring the snow and trailconditions, maintaining signs, clearing obstacles, etc.). That clubgenerally also will create a map that can be purchased by visitors tothe area. The map will generally include points of interest in the area,and advertisements and coupons associated with the businesses on themap. Those maps can be sold at gas stations, bars, restaurants, andonline for use by riders who plan to visit the area. The cost of the mapand the cost of the advertisements are used to fund the club's upkeep ofthe trail system in that area.

This arrangement is convenient for upkeep of trails, but can beinconvenient to trail users. There are a number of reasons for this. Forexample, trail maps are generally organized by region, and riders maywish to travel among a number of regions whose maps are maintained bydifferent clubs. Furthermore, trail riders may wish to have coordinatedmaps of points of interest that are not limited to the regions coveredby a particular club, and not limited those businesses that choose toadvertise with that club.

In connection with these difficulties, trail riders will often opt topurchase and download an electronic copy of the trail map, and plantheir routes prior to starting that trip. However, once that trip isplanned, the user will typically print out the trail map for use on therecreational vehicle for use.

In addition, recreational vehicle usage, because it typically occurs inoff-road, rural areas, may cause a rider to become stranded in alocation remote from any other individual, and far from a maintenancefacility for that vehicle. For example, in the case of a snowmobile, auser may have an equipment malfunction or other issue far from a repairshop, or even from a road. In such cases, even if that rider had a cellphone with them (and even if that rider had service in the rural areawhere such a maintenance issue occurs) it may be difficult to diagnoseproblems with the recreational vehicle.

Beyond these existing issues in recreational vehicle usage andnavigation, there is also no convenient way to coordinate route plansamong riders, despite the fact that it is common to take such trips ingroups. Accordingly, improvements in the rider experience, and invehicle integration with the rider experience, are desired.

In one illustrated embodiment of the present disclosure, an interactivesystem for use in connection with recreational vehicle usage includes aserver system. The server system includes an off-road trail databasecontaining trail data, trail condition information, andpoints-of-interest information, as well as a trip mapping systemaccessible by any of a plurality of riders, the trip mapping systemallowing a rider to create a planned route based on the data in theoff-road trip database and navigate the planned route. The server systemfurther includes a trail maintenance interface accessible by usersaffiliated with an authorized group to edit at least a portion of thetrail data, trail condition information, and points-of-interestinformation associated with the authorized group. The server systemincludes a location data management system configured to receivelocation data, the location data management system allowing a rider topublish his or her location information to one or more other riderswithin the mapping system. The server system further includes a userfeedback interface configured to receive trip data from riders forpublication to one or more other riders using the interactive system,the trip data including information describing an actual route and userdata associated with the actual route.

In another illustrated embodiment of the present disclosure, a method offacilitating usage of a recreational vehicle includes receiving, fromusers affiliated with a plurality of authorized groups, trail data,trail condition information, and points-of-interest information fromareas affiliated with the authorized groups, respectively. The methodfurther includes receiving a request from a user device to define aplanned off-road route in one or more of the areas, and generating a mapassociated with the planned off-road route, the map including trailcondition information and points-of-interest information received. Themethod also includes receiving location information from acommunications device at a location of a recreational vehicle operatedby the user during travel along the planned off-road route, andpublishing the location information to one or more other users based onpermissions set by the user. The method includes receiving user feedbackinformation associated with the planned off-road route from the user.

In yet another illustrated embodiment of the present disclosure, anapplication embodied on a computer-readable medium is disclosed that isexecutable on a computing device and includes program instructions that,when executed, are configured to cause the computing device to receiveuser input requesting an off-road route, the user input including one ormore ride parameters. The computing device is also configured to definean off-road route based at least in part on the one or more rideparameters and trail condition data received from one or morethird-party sources, and present the off-road route to the user via amap display, including presenting a plurality of route variations to theuser, the route variations including display of one or more rideparameters of the route variations compared to the off-road route. Thecomputing device is further configured to receive user selection of adesired off-road route for traversal.

In still another illustrated embodiment of the present disclosure, acomputer-readable medium comprising computer-executable instructions isdisclosed that, when executed, perform a method for integrating riderexperience with recreational vehicle performance. The method includesreceiving from a user a selection of a planned route for a recreationalvehicle at a computing device associated with the recreational vehicle,and receiving at the computing device, via a communication interfaceconnected to a control unit of a recreational vehicle, data regardingoperation of the recreational vehicle. The method further includesdisplaying a user interface to a user, the user interface includinginformation associated with the planned route and at least a portion ofthe data regarding operation of the recreational vehicle, andcommunicating data to a remote system from the computing device, and atleast a portion of the data regarding operation of the recreationalvehicle. The method also includes receiving from the remote system oneor more instructions for display to the user regarding maintenance orrepair tasks to be performed on the recreational vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an interactive system for use in connection withrecreational vehicle usage, according to an example embodiment of thepresent disclosure;

FIG. 2 illustrates an example server and database useable in theinteractive system of FIG. 1;

FIG. 3 illustrates an example application useable on a mobile device andintegrable with the interactive system of FIG. 1;

FIG. 4 illustrates an example arrangement for integrating a recreationalvehicle into an interactive system as illustrated in FIG. 1;

FIG. 5 illustrates an alternative arrangement for integrating arecreational vehicle into an interactive system as illustrated in FIG.1;

FIG. 6 illustrates an example dataflow for management of trail datauseable within the interactive system of FIG. 1;

FIG. 7 illustrates an example user interface used for managing traildata by a user or recreational vehicle rider;

FIG. 8 illustrates an example user interface used for planning a routeby a user or recreational vehicle rider;

FIG. 9 illustrates an example user interface used for viewing route databy a user or recreational vehicle rider;

FIG. 10 illustrates an example user interface used for viewing points ofinterest along a planned route by a user or recreational vehicle rider;

FIG. 11 illustrates an example user interface used for tracking a routeby a user or recreational vehicle rider;

FIG. 12 illustrates a second example user interface used for tracking aroute by a user or recreational vehicle rider;

FIG. 13 illustrates an example user interface used for creating a newroute by a user or recreational vehicle rider;

FIG. 14 illustrates an example user interface used for displayinghazards along a route to a user or recreational vehicle rider;

FIG. 15 illustrates a second example user interface used for displayinghazards along a route to a user or recreational vehicle rider;

FIG. 16 illustrates an example user interface used for displayinglocations of selected other individuals along a route to a user orrecreational vehicle rider;

FIG. 17 illustrates an example user interface used for displayingdetails regarding a selected individual to a user or recreationalvehicle rider;

FIG. 18 illustrates an example user interface used for displayingweather data along a trail to a user or recreational vehicle rider;

FIG. 19 illustrates an example user interface used for displaying traildetails to a user or recreational vehicle rider;

FIG. 20 illustrates an example user interface used for integratingsocial media features into a trail rider system for use by a user orrecreational vehicle rider;

FIG. 21 illustrates an example user interface used for displayingrecreational vehicle speed data to a user or recreational vehicle rider;

FIG. 22 illustrates an example user interface used for displayingrecreational vehicle fuel usage to a user or recreational vehicle rider;

FIG. 23 illustrates a flowchart of a method for facilitating usage of arecreational vehicle, according to an example embodiment;

FIG. 24 illustrates a flowchart of a method for integrating riderexperience with recreational vehicle performance, according to anexample embodiment.

FIG. 25 is a block diagram illustrating components of a multi-functiongauge having a full color display screen interacting with a mobiledevice and other vehicle components;

FIG. 26 is a block diagram illustrating vehicle sensors coupled to anelectronic control unit (ECU) and components of a vehicle controlled bythe ECU through the gauge or mobile device;

FIGS. 27 and 28 illustrate additional details of a multi-function gaugeof one embodiment of the present disclosure;

FIGS. 29 and 30 illustrate display screens and control buttons of thegauge of FIGS. 27 and 28; and

FIGS. 31-34 illustrate the position of the multi-function gauge anddisplay screen located within utility vehicles, all terrain vehicles,and snowmobiles.

DETAILED DESCRIPTION OF THE DRAWINGS

Various embodiments of the present invention will be described in detailwith reference to the drawings, wherein like reference numeralsrepresent like parts and assemblies throughout the several views.Reference to various embodiments does not limit the scope of theinvention, which is limited only by the scope of the claims attachedhereto. Additionally, any examples set forth in this specification arenot intended to be limiting and merely set forth some of the manypossible embodiments for the claimed invention.

The logical operations of the various embodiments of the disclosuredescribed herein are implemented as: (1) a sequence of computerimplemented steps, operations, or procedures running on a programmablecircuit within a computer, and/or (2) a sequence of computer implementedsteps, operations, or procedures running on a programmable circuitwithin a directory system, database, or compiler.

As briefly described above, embodiments of the present invention aredirected to systems and methods that provide for a guided, interactiveuser experience for use in off-road or recreational vehicle usage. Thiscan include, for example, usage in connection with motorcycle,all-terrain vehicle, snowmobile, or other types of recreationalvehicles, and involves aggregation of user feedback regarding trailinformation and points-of-interest data, club information regardingtrail conditions, and weather, hazard, and vehicle data to enrich therider experience. By providing users with shared information regardingtrail condition, length, difficulty, weather, and points of interestdata, while also displaying to a rider various data regarding his hervehicle on a display alongside weather or hazard data and locations ofother riders along a particular trail, that user's experience can beimproved, by ensuring that the user is connected with the people,places, and vehicle experiences that will encourage the user to continueuse of recreational vehicles.

Referring now to FIG. 1, an interactive system 100 is shown for use inconnection with recreational vehicle usage, according to an exampleembodiment of the present disclosure. The interactive system 100includes a server system, shown as recreational vehicle portal server102, hosting a trail and rider database 104. The recreational vehicleportal server 102, referred to herein as server 102, generallycorresponds to one or more computing systems configured to store andprocess data associated with one or more riders of recreationalvehicles, as well as data associated with trails of interest to thoseriders. Such data can be located in the trail and rider database 104, orcan be received from any of a plurality of data providers, such as dataproviders 106 a-e, discussed below.

In the embodiment shown, the server 102 is accessible by any of aplurality of users of recreational vehicles 108, which can includeoff-road vehicles, such as all-terrain vehicles or snowmobiles, and canalso include other types of recreational vehicles such as motorcycles.It is noted that, although in the embodiment illustrated in FIG. 1 onlysnowmobiles are shown, it is understood that other types of recreationalvehicles could be used as well, according to the various aspects of thepresent disclosure.

The server 102 is also accessible via a plurality of other computingdevices, such as a mobile device 110 (e.g., a mobile phone or tabletdevice) and/or a computing device 112 having a web browser installedthereon. However, for some uses of the server 102, a computing device112 and associated web browser may be required to enable somefunctionality, while in other example embodiments, an applicationinstalled on a mobile device 110 may be required. For example, asdiscussed in connection with some embodiments of user interfacesdiscussed below, location-based services in which a user's location ispublished, and where loyalty-based social networking and locationservices are provided may require use of a mobile device 110, while somefeatures, such as entry of trail maintenance and/or condition data mayrequire entry through a specific web interface by particular individuals(e.g., authorized members of a club responsible for maintaining thetrail). In the example shown, first and second computing devices 112 a-bare shown, representing a user acting as a rider (computing device 112a) and a second computing device associated with a member of atrail-managing club (computing device 112 b), respectively.

In the embodiment shown, a plurality of third-party data services isintegrated with the information delivered to the users of devices 110,112 a-b. The data services, provided by data providers 106 a-e, allowfor integration of a variety of types of data in a user interfacecoordinated by server 102. In the embodiment shown, the data providers106 a-e include a map data provider 106 a, a weather data provider 106b, a GIS data provider 106 c, an advertising data provider 106 d, and atrail condition data provider 106 e.

The map data provider 106 a delivers map services to the server 102,with which various data overlay services can be provided including trailor route data, trail or route plans, GIS data, or other types ofinformation as discussed herein. In some cases, the weather dataprovider 106 b can provide weather data such as forecast data, or couldalternatively (or in addition) provide current weather or radar data foroverlay on the map data received from the map data provider 106 a, fordelivery to a user who is a rider of a recreational vehicle 108, forexample to allow that rider to view forecast or current inclementweather conditions. The GIS data provider 106 c similarly providesoverlay information allowing for definition of topography, locations ofproperties, locations of cities/towns, trails, roads, and otherinformation.

In some embodiments, the advertising data provider 106 d deliversadvertisements to users who are riders. The advertising systems of thepresent disclosure can take many forms. For example, in some cases, whena particular route is being displayed, advertising corresponding tobusinesses located along that route can be displayed to the user. Insuch cases, the advertising is managed by the server 102, or specificadvertising businesses are selected by one or more trail clubs thatmanage a particular area of a trail system. Correspondingly, and asdiscussed in further detail below, proceeds from advertising may beapportioned to the trail club in the area based on the frequency ofdisplay of advertising, or other metrics. As such, trail clubs cancontinue to receive revenue from advertising that currently is receivedbased on placement of advertisements on printed trail maps associatedwith the area the trail club maintains.

In the embodiment shown, the trail condition data provider 106 eprovides to the server 102 trail condition data. This trail conditiondata illustratively includes reported data from trail clubs or users,but typically corresponds to third party trail condition data, such asmay be monitored by a governmental organization (e.g., the department ofnatural resources for the state in which the trail is located), or otherregional groups.

In an illustrated embodiment, other data providers are integrated withsuch a system as well. For example, in the case where social networkingservices are provided for riders using the services provided by system100, such services are either integrated into the server 102 or providedby a further data provider 106.

In addition to the data providers and third party contributors, a dealer114 is illustratively provided access to the server 102, for example tomanage, store, and access vehicle maintenance records associated withparticular vehicles. In such embodiments, the dealer 114 stores suchrecords locally, and receives maintenance and/or repair information froma vehicle 108 from the server 102, or alternatively stores all suchmaintenance and repair information in the database 104, associated withthe server 102.

As illustrated in FIG. 1, the various data providers 106 e arecommunicatively interconnected with the server 102 via a network 116,such as the Internet. Additionally, such a network is used by users ofmobile device 110 or computing devices 112 a-b, as well as dealers 114for communicative interconnection to the server 102.

Referring now to FIG. 2, additional details regarding the server 102 andthe trail and rider database 104 of FIG. 1 are shown. The server 102generally provides a plurality of interfaces and services by which dataare aggregated and delivered to users who are riders of recreationalvehicles. As further discussed herein, the interfaces and servicesdelivered to those users include trip planning, navigation, socialnetworking and trail feedback, and vehicle maintenance and repairservices, among others.

In the embodiment shown, the server 102 includes a mobile applicationinterface 202 and a web interface 204 that provide user access tovarious mapping, planning, and on-trail data services. The web interface202 allows a user to connect to the server 102 via a computing device112, and register his or her recreational vehicle with the server 102.The mobile application interface 202 provides analogous functionalityvia a downloadable application stored on a smartphone or tablet device,such as mobile device 110. Furthermore, through the web interface 204 ormobile application interface 202, the user plans a route that the userintends to take on his/her recreational vehicle, and the server 102,based on the trail condition data, confirms that the selected route ispassable. The web interface also allows users to select their skilllevel, and presents various possible available routes based on thevehicle type defined by the user (snowmobile, all-terrain vehicle,motorcycle, etc.) and associated skill levels for those routes. Forexample, a beginner motorcycle rider has routes presented to him or herthat are limited to non-technical street routes, while a snowmobilerider is routed solely on trails, since snowmobiles are not typicallyridden on roads. The route displayed includes, for example, a distanceand expected time for traveling the route based on the user's skilllevel. Other data, such as fuel needed along the route, or display ofalternative routes nearby, is delivered as well. Various other possibleroute selection features are possible as well, as further discussedbelow.

In addition to the route selection features, the mobile applicationinterface 202 and web interface 204 each allow the user to “preview” thetrip that is selected, for example by providing a user-perspective“fly-through” view or simulation of a selected route, based on trailphotos or videos collected in the database 104. Additionally, a userfeedback interface available in the mobile application interface 202 andweb interface allows a user to indicate that he or she has taken aparticular route, and allows that user to enter a review of theirexperience when taking that route. This information is used bysubsequent riders, during trip planning, since it can be made visible inassociation with the route planning features discussed above.

The mobile application interface 202 and web interface 204 also allowfor tracking one or more other individuals' locations along a trail, forexample to trace where fellow riders are along a trail, or to monitorprogress of friends or relatives who are on a trail ride. Additionaldetails regarding the features presented by the mobile applicationinterface 202 are discussed below in connection with FIG. 3, andexamples of user displays generated by such interfaces are discussed infurther detail below in connection with FIGS. 7-22.

In addition to the mobile application and web interfaces 202-204, in theembodiment shown the server 102 includes a plurality of data interfaces.These data interfaces can include, for example, a third party dataprovider interface 206, which receives and manages data associated withdata providers 106 a-e, as well as a club portal interface 208. The clubportal interface 208 is configured to manage communication with membersof regional trail clubs. These trail clubs generally maintain andmonitor the status of trails in a particular geographical area. Membersof the trail club can therefore use the portal interface 208 to updatetrail routes, trail conditions, provide advisories to trail riders(e.g., instructions to avoid departing trails that pass through privateland, tips regarding scenic locations or routes, etc.), and notesregarding local regulations. An advertising manager component 210coordinates with the club portal to communicate with an advertisingprovider 106 e, to control the types of advertisements provided to usersof the mobile or web interfaces 202, 204, thereby limiting theadvertisements displayed to a user to those approved by the club, orthose in the same geographical area as the club. As further discussedbelow in connection with FIG. 6, the advertising manager also managesrevenue apportionment across trail clubs and other entities, to provideincentives to contribute to the overall system 100.

In addition, a dealer interface 212 can be included, which associatesone or more of the riders using the services of the server 102 with aparticular dealer. The dealer interface 212 is used in a number of ways.In some cases, the dealer interface is used to communicate error codesor diagnostic data received from one or more recreational vehicles 108,for example to receive in response repair instructions or maintenancetips from the dealer(s) associated with those vehicles. Accordingly,riders of recreational vehicles are ensured of vehicle repair supportduring trail rides, while dealers receive notifications of possiblerepairs, allowing the dealer to provide additional value to customerswho use such vehicles that support diagnostic data communication via theserver 102.

The database 104 stores various types of data used by the server 102,including the various interfaces 202-210, to generate, along with dataproviders 106 a-e, services to be presented to users who are riders ofrecreational vehicles. In the embodiment shown, the database 104includes trail data 220 used for route planning purposes, which caninclude routes, property details, and trail condition data as may bereceived from a club member or third party data provider. The database104 can also include trail photos 222, either submitted by riders whohave previously traveled along the trails, or from a trail photo capturesystem useable to generate a “fly-through” sequential photo playbackthat simulates traveling along the trail. The database 104 furtherincludes user feedback 224, which can include reviews of a trail, aswell as ratings of the trail (e.g., difficulty, time required totraverse, etc.) as well as notes regarding points of interest, or otherfeatures.

In the embodiment shown, the database 104 includes rider location data226, which can be received from a mobile device hosting a complementaryapplication via mobile interface 202, or directly from a GPS-equippedrecreational vehicle. The rider location data 226 is used to provideturn-by-turn navigation along on- and off-road routes, and is alsoselectively published to other riders, for example other riders in agroup of riders who wish to track each other's progress along a trail.Additionally, points-of-interest data 228 is received from users or clubmembers, and includes specific scenic locations or businesses alongsidetrails. The points-of-interest data is displayed to the users. Forexample, the data is overlaid on a mapping display as illustrated below.

In some embodiments, the database 104 includes vehicle maintenance data230 and vehicle repair data 232. The vehicle maintenance data 230includes information associated with general vehicle maintenance tipsthat are provided to the user, as well as specific maintenance recordsassociated with the user's recreational vehicle. The vehicle repair data232 includes instructions for responding to various malfunctions thatmay occur on such vehicles, for example including instructions forphysically repairing the vehicles, or for responding to error codesreceived at the server 102 that are generated by an electronic controlunit of a recreational vehicle, as discussed further below in connectionwith FIGS. 4-5. This maintenance and repair data is, for example,provided by the user via the mobile application or web interfaces 202,204, or from a dealer 114 as illustrated in FIG. 1.

In operation, the server 102 uses the data stored in database 104 for avariety of applications that are provided to a user via the web ormobile application interfaces 204, 202, respectively. Accordingly, inFIG. 3, an example embodiment of a mobile application 300 isillustrated, which represents functionality that is made available to auser of a mobile device (e.g., device 110) that is communicativelyconnected to the server 102.

In the embodiment shown, the mobile application 300 resides in a memory302 of a mobile device 110, which typically includes a programmablecircuit, display, camera, and global positioning system (GPS) antenna.Generally, the mobile application 300 is configured to interface to themobile application interface 202 of FIG. 2, on the server 102. By way ofthis communicative connection, the mobile application 300 delivers anumber of services to a user who is a rider of a recreational vehicle.In particular, the mobile application includes, in the embodiment shown,a route planner component 304, a buddy tracker component 306, a routeflythrough component 308, and a points-of-interest component 310. Themobile application 300 also includes, for use during the trip,turn-by-turn navigation component 312 and a vehicle interface 314.

The route planner component 304 provides a mechanism by which a userselects and plans one or more routes on which to take a ride withhis/her recreational vehicle. The route planner component 304 includes arules engine that operates to automatically plan a “best” route for auser given a set of parameters. For example, the route planner component304 determines a distance, duration, difficulty level, and expected fuelconsumption of a particular ride, based for example on map and GIS datareceived by data providers. The route planner 304 includes selectableoptions that allow a user to either select a particular destination (inwhich case the best route between a start point and that destination issupplied) or to route a user on a loop of a predetermined duration,based on skill of the user and starting location. In some embodiments,the route planner component 304 is configured to search for and/orpresent to a user a set of routes from which that user can select adesired route, with the routes varying in duration and/or difficulty.The route planner component 304, in such embodiments, is directed by auser to select only “safe” or “challenging” rides for display to theuser, and is configured according to rider skill level.

In some embodiments, the route planner component 304 further includes aride finder, which locates previously-taken routes of that user/rider orother riders. In such embodiments, the route planner component 304causes display of trails and/or destinations that are recommended byother riders, and includes, for example, text describing the ride ortrail, pictures, and video highlights provided by other riders forviewing by the user of the application 300, to allow that user to selecta ride or trail recommended by others. In addition, the route plannercomponent 304 allows users to save and share their own historicalroutes, as well as upload to the server pictures, videos, anddescriptions of those routes.

In some embodiments, the route planner component 304 also accounts for,when assisting in planning a route, whether that route will cross anyprivate land. In some embodiments, the route planner component 304, whendetermining a route to be displayed to a user, is configured (e.g., at auser's option) to display only routes that avoid crossing private land.

The buddy tracker component 306 allows a user to publish his/herlocation to be viewable by others during a trip, and also allows theuser to view others' locations on a map interface, for example asillustrated in FIG. 16, discussed below. In some embodiments, the buddytracker component 306 coordinates with the route planner to determine ifthe rider, during the course of a ride, is on a collision course withanother rider, and can notify that rider accordingly. For example, asecond rider may be ahead of the rider having the application running,but that second rider may have stopped, for rest or due to an equipmentmalfunction. The rider, if traveling at a high rate of speed, may nothave adequate time to see that second rider stopped on a trail beforehe/she needs to stop.

Additionally, the route flythough component 308 allows playback andpausing of a route traveled, as well as managing a virtual “fly-through”or simulation of a route. This “fly-through” corresponds to a projected,360-degree view of a route, based on captured images along a route. Insome cases, the trail photos 222 stored in database 104 includes a setof photographs or videos used for such a “fly-through” feature.

The points-of-interest component 310 is configured to display one ormore points of interest associated with a selected route. In some suchembodiments, the points-of-interest component 310 includes a feature inwhich the points-of-interest component associates specific points ofinterest with a particular trail club along which those points ofinterest are located. In such embodiments, the point of interestinformation that is displayed is limited to the specific points ofinterest provided by that trail club, or in the area managed by thetrail club.

The turn-by-turn navigation component 312 provides, once a user hasselected a particular route, turn by turn directions for following thatroute, analogous to those turn by turn directions available via currentroad-based navigation systems, but managed based on GIS and trail datareceived from a plurality of sources and data providers.

The vehicle interface 314 also provides additional functionality duringa ride, and receives data from a vehicle that indicates a current ofhistorical operational state of the vehicle. For example, in someembodiments, the vehicle interface 314 receives data from an electroniccontrol unit of a vehicle, and is configured to display such informationon a display of a mobile device (e.g., in the case of fuel consumption,speed, throttle position, or other similar operational parameters), orcommunicates such data, such as error codes or other issues, to a serverfor relay to a dealer or repairperson. In those cases, the dealer orrepairperson communicates with the user of the application 300, forexample to provide information regarding how to fix issues on therecreational vehicle.

Audible interface 316 can be used in a variety of contexts, andsimplifies operation of the mobile application by presenting the userwith audible updates as to the route, turn by turn directions, locationsof buddies along the trail, or points of interest that are beingapproached. This allows the user to keep his or her eyes on the trailwhile traveling.

In addition to the above, the mobile application also includes a userfeedback component 318. The user feedback component 318 is used duringor after a ride, for example to provide that user's informationregarding the perceived difficulty, length, or feedback regarding pointsof interest encountered during the ride. In some embodiments, the userfeedback component 318 includes a social networking aspect in which theuser “checks in” or comments regarding businesses that are located alonga trail, and provides tips to other riders regarding those points ofinterest.

In accordance with the various components and interfaces of FIG. 3, itis noted that the mobile application is configured to generate aplurality of user interfaces, examples of which that illustrate theabove-described functionality being shown in FIGS. 7-22, describedbelow. Furthermore, although the functionality of the mobile application300 is discussed in terms of a mobile device system, it is recognizedthat most, if not all, of the same functionality is provided via a webinterface accessible via a browser of a desktop or laptop computingsystem. In some cases, where mobile device functionality such as GPS orcamera features are used, corresponding features of the mobileapplication 300 may be unavailable via a browser-based version of theapplication.

Referring now to FIGS. 4-5, example embodiments of systems are shownthat integrate communication from a recreational vehicle to the server102. In general, the embodiments illustrated herein communicate with theserver 102, either directly as illustrated in FIG. 1 or are coordinatedthrough the vehicle interface 314 of the mobile application 300, toprovide to that user “on-trail” information.

In the embodiment shown in FIG. 4, a first embodiment of integratingcommunication of a recreational vehicle 108 into the system 100 of FIG.1 is shown. In the embodiment shown, the recreational vehicle 108 has anelectronic control unit (ECU) 402, which is communicatively connected,as is known, to various vehicle subsystems, such as an engine 404, userinputs 406 (e.g., throttle, braking, or other input information), aswell as sensor data 408 (e.g., ambient and exhaust temperatures, fuellevels, component sensors, etc.). The ECU 402 is typicallycommunicatively connected to a controller area network (CAN) interface410, which exposes various parameters of operation of the vehicle 108.In the embodiment shown in FIG. 4, an integrated controller 412 iscommunicatively connected to a gauge or display 414 and a communicationinterface 416, which is, for example, a cellular or satellitecommunication interface, communicatively connectable to server 102. Thecontroller 412 illustrative includes a programmable circuit and memory,and as such cooperates with the display 414 to provide much of thefunctionality discussed above with respect to the mobile application300. In addition, various other components, such as a GPS or audibleinterface, are included in the overall recreational vehicle system aswell, to provide additional functionality that is desired nativelywithin the recreational vehicle. Additional details of this embodimentare described below with reference to FIG. 25.

In contrast to FIG. 4, in FIG. 5 a mobile device 110 is used, withintegration at the CAN interface 410. This is accomplished, for example,by connecting a dongle 420 or other wired-to-wireless or direct-wiredconnection between the ECU 402 and the mobile device 110. In someembodiments, a dongle 420 implements a Bluetooth, radio frequency (RF)or some other short-range wireless standard for wireless communicationbetween the ECU and a communication interface 450 of the mobile device110. In such an arrangement, the mobile device 110 includes a controller452 that receives data from the ECU 402, and integrates a display 454and various peripheral devices 456 (e.g., GPS, camera, etc.), forintegration of vehicle operational data with data received at the mobiledevice, in accordance with the functionality discussed above inconnection with FIG. 3.

It is noted that, via the CAN interface 410, a variety of types ofinformation are provided for display at the vehicle, or forcommunication to the server 102. In various embodiments, vehicle datareceived from the ECU 402 includes, for example: engine revolutions perminute; vehicle speed; coolant temperature; battery voltage; fuel level;throttle position; pedal position; fuel consumption rate; vehicle range;engine load; barometric pressure; air intake temperature; exhaust airtemperature; gear indication; spark timing; operational hours; drivestatus; and trouble codes. Other types of information is received viathe CAN interface 410, depending upon the particular type of vehicle andfeatures included thereon. Examples of display information thatintegrates route and vehicle information are illustrated in the userinterfaces of FIGS. 21-22.

Referring now to FIG. 6, an example data administration arrangement 600is shown which is useable in connection with the system 100 of FIG. 1,and which illustrates how various types of data that is received fromusers of various types (e.g., riders, trail club members, advertisers,etc.) are received and managed, and how attendant revenue is managed anddistributed across those entities as well. In the embodiment shown,clubs 602, which generally include trail maintenance organizations whotypically receive revenue from advertisements on trail maps, arevalidated as recognized organizations (step 604). Validated clubs andassociated members can then provide trail data, including new and/orupdated trail data, to be stored in the database 102 (step 606). Thattrail data is validated (step 608), and the validated trail data is thenmerged with trail data maintained by a larger aggregator of trail data,such as the trail maps maintained by USTRAILS.org or some otheranalogous organization (step 610), prior to storage in the database 102of trail data 220. For example, the aggregated trail data includestrails generally entirely on public lands, whereas the club-maintainedtrails may include trails on private lands where a club has negotiatedsome right-of-way or through-route with the landowner.

In addition to receiving club and third party trail data, users provideinformation regarding trails (step 612), either as aggregate to the clubtrail data (e.g., providing reviews of the club-provided trails, ordirectly providing additional comments regarding the public trails. Theinformation regarding the club-sponsored trails includes, for example,trail condition information, review information regarding the quality,difficulty, or other information regarding the trails (step 614).

To support the aggregation of trail data, a revenue model isincorporated into the overall data administration at the server, and isincluded, for example as part of the advertising manager component 210of the server 102. In the embodiment shown, the revenue model includesgeneration of revenue 620 from various sources, such as originalequipment manufacturers 652 who wish to be integrated into such a systemas well as revenue from downloads of a mobile application 300 (shown asapplication revenue 652), and advertising revenue 654. In thearrangement shown, trail clubs and other trail aggregators areillustratively compensated out of this revenue, either directly byadvertisers or as subsidized by application downloads or OEMs directly.

In addition, it is noted that a mobile application 300 is downloadableby various individuals, such as a vehicle owner 660, a rider 662, or athird party vehicle owner 654, which represents an owner of arecreational vehicle that is not supported by the overall system 100,for example because it is manufactured by a non-participant OEM. It isnoted that some features and functionalities discussed above, which aretypically provided to users of a mobile application, may not beavailable to users of a mobile application in connection with arecreational vehicle manufactured by a non-participant OEM. For example,integration of vehicle data and application data, such as is used todisplay vehicle data within the application 300, or to send error codesto server 102 to receive on-trail repair and maintenance support, is notprovided in such cases. However, in each case, the application is usedby these individuals 660-664 to provide trail reviews, as well asup-to-date trail condition information (step 666), which is integratedwith the club or third party information, as discussed above inconnection with steps 612-614.

Now referring to FIGS. 7-22, various example user interfaces of a mobileapplication 300 are illustrated, which show some of the exampleoperations that are provided for by the system 100 of FIG. 1, asreflected in a display of a mobile device 110, before, during, and aftera ride via a recreational vehicle. As discussed above, the variousfeatures and functionalities illustrated in FIGS. 7-22 may at least inpart be made available via a web interface to a user of a computingdevice and associated web browser, or via a display integrated into arecreational vehicle (as illustrated in FIG. 4). In an alternativeembodiment shown in FIG. 25, the features of FIGS. 7-22 are displayed ona display of gauge 414 located within the vehicle.

Referring first to FIG. 7, an example user interface 700 used formanaging trail data by a user or recreational vehicle rider is shown.The user interface 700 represents a general menu interface that allows auser to use a route tracking component of the web or mobile application,to view or plan various routes. In the embodiment shown, the userinterface 700 includes a route tracking option 702, a route planningoption 704, and a route import option 706.

The route tracking option 702 allows a user to select from among aplurality of pre-saved routes, or to create a new route using a mappingand direction creation feature. The route planning option 704 allowsthat same user to view a set of pre-defined, shared routes, and to viewpoints of interest, difficulty levels, and other types of informationassociated with that route. A route import option 706 allows the user toimport data, such as may be included in a route description file (e.g.,a flat file or markup language file defining route coordinates) to beused as a route to be traveled.

In the embodiment shown in FIG. 7, a number of additional mappingoptions are displayed on the user interface 700 as well. A routes option708 allows display of alternative routes between a start and end point,and a way-points option 710 allows a user to define one or morewaypoints along a selected trail that are used as rest locations, or todefine the desired trail to the automatic mapping features of thesystem. An events option 712 allows a user to define rest times,specific locations and times, or specific occurrences along a trail thatmay be of interest. An information option 714 allows the user to providedescriptive information about the trail to be traveled, for example toprovide that trail to others who will be along on the trip.

Furthermore, general options that allow user navigation within theapplication 300 are included on the illustrated user interface as well.These include general pieces of information that may be of interest tothe user, such as a weather option 720, a dealers option 722, a servicesoption 724, and a routes option 726. Additional types of optionsinclude, for example in a hidden menu that can be reached via a “more”option (shown as ellipses 728). The weather option 720 causes a weatherscreen to be displayed, for example weather in an area in proximity to aselected route, as illustrated in FIG. 18. The dealers option 722 allowsa user to view nearby dealers or that particular individual's dealer,for example to allow that individual to contact the dealer while on thetrail. In one embodiment, a parts check option allows the user to checkfor the availability of a certain repair part or accessory at anidentified dealer on the trail route. The services option allows theuser to view additional services available to the user, for exampleregarding maintenance or repair services.

FIG. 8 illustrates an example user interface 800 that is used forplanning a route by a user or recreational vehicle rider. The userinterface 800 includes saved routes 802 of the rider, as well asbookmarked routes 804 of other riders, and nearby routes 806 that havebeen published by other riders. A routes listing 808 displays availableroutes, and a new route option 810 allows the user to initiate anauto-mapping process by which the user defines a new route betweenpoints, or point-to-point, using waypoints defined by the waypointsoption discussed above in FIG. 7.

FIG. 9 illustrates an example user interface 900 that is used forviewing route data by a user or recreational vehicle rider, for exampleonce a particular route has been selected. In the embodiment shown, aroute usage option 902 illustrates a frequency of use of that route, andan edit route option allows the user to change the route based onhis/her preferences. The interface 900 also includes a route map 906(shown schematically), and route contours 908 that illustrate elevationand distance of a particular route.

FIG. 10 illustrates an example user interface 1000 that is used forviewing points of interest along a planned route by a user orrecreational vehicle rider. The interface 1000 includes a start pointand endpoint 1002 a-b of a route 1003, as well as flagged points ofinterest 1004 along the route 1003, on a map display interface 1006. Thepoints of interest 1004 illustratively include scenic views, businesses,or other information. An information panel 1008 provides informationregarding the route generally; upon selection of one or more of thepoints of interest, additional details regarding that point of interest,or reviews by other users, is displayed in the panel 1008.

FIGS. 11-12 illustrate an example user interface 1100 used for trackinga route by a user or recreational vehicle rider. The route tracking userinterface provides a playback of a route traveled by a user, for exampleto allow that user to revisit his/her route upon completion of theroute. Additional details of the route storage and playback arediscussed below. The route tracking interface 1100 displays the mapdisplay interface 1006, but includes location information, as well as aplay/pause option 1102. The route tracking interface 1100 includes aninformation bar 1104 that illustrates distance traversed, time required,and optionally includes a variety of other types of information, such asfuel consumed, speed at each location (if vehicle data is available) orother information associated with the ride. As seen in FIG. 12, a routemanagement option 1106 allows a user to save or delete the route thatwas traversed.

FIG. 13 illustrates an example user interface 1300 used for creating anew route by a user or recreational vehicle rider, as well asillustrating historical information regarding routes. The user interfaceincludes an add new trip option 1302 which instantiates the routeplanning features described above. The user interface 1300 also includesa history 1304 of recorded trips, which is selected for tracking andplayback as illustrated in the user interface 1100 of FIGS. 11-12.Additionally, accumulated statistics 1306 are displayed, showing, forexample, total miles logged by the rider, as well as typical ride times,distances, and other historical information.

FIGS. 14-15 illustrate a further example user interface 1400 that isused for displaying hazards along a route to a user or recreationalvehicle rider. The user interface 1400 generally illustrates a mappingarea 1402, as discussed above in connection with the route planner andpoints of interest data, but in this view, one or more hazards 1404 aredisplayed along a selected route. Example hazards, such as reportedcrashes, fallen trees, closed roads, or other hazardous conditions suchas snow grooming equipment on the trail are marked. Upon selection ofthe hazard 1404, additional details regarding the type and duration ofthe hazard are displayed, as seen in FIG. 15. Additionally, an alternateroute option 1406 allows a user to have an alternate route generated toavoid the hazard, using the routing components discussed above.

FIG. 16 illustrates an example user interface 1600 used for displayinglocations of selected other individuals along a route to a user orrecreational vehicle rider. The user interface 1600 accordinglyimplements a “buddy tracker” component of the system in which a userselects one or more other riders to track along a preselected route. Thebuddy tracker illustrates relative positions of those riders along thetrail. As seen in FIG. 16, upon selection of one of the icons 1602 on amap display 1604 illustrating other riders, information about thatrider, such as his/her name and relative location, are displayed. Insome embodiments, the buddy tracker feature implemented using the userinterface 1600 is integrated with the hazards display, for example inthe event that a user rides too close to another rider, therebytransforming the buddy tracker into a hazard display, showing a warningto those riders (and nearby riders).

FIG. 17 illustrates a still further example user interface 1700 used fordisplaying details regarding a selected individual to a user orrecreational vehicle rider. The user interface 1700 is displayed, forexample, upon selection of a buddy or display of a user profile to showadditional information about that other rider. The illustrated userinterface includes an information area 1702 including name andphotograph of the rider, as well as statistics 1704 regarding thatrider, such as miles traveled, frequency or last ride times, or sharedroutes 1706 with that rider. Optionally, a “follow” option 1706 isincluded as well, allowing the user to track that rider, for example toadd that rider to his/her buddy tracker, or to view additional detailsregarding that user, or to integrate various social networking featuresuseable in connection with that user (analogous to a “friend” orfollower in various social networking systems currently available).

FIG. 18 illustrates an example user interface 1800 used for displayingweather data along a trail to a user or recreational vehicle rider. Theuser interface 1800 includes a map display 1802 that includes a route1804 selected by the user, and optionally includes an icon 1806illustrating that user's current location on the route. The map display1802 includes an overlay of weather information 1808, either in iconform (as shown) or as radar data, illustrating locations and detailsregarding portions of the trail experiencing inclement weather. Otherinformation such as, for example, warnings (appear large and then shrinkon display), snow depth, dealer locations, trail overlays, and approvedbackcountry routes may be provided on the map display. Additionalpoints-of-interest displayable on the display include lodging, medical,shelter, rest areas, gas, and landmarks.

FIG. 19 illustrates an example user interface 1900 used for displayingand reporting trail details to a user or recreational vehicle rider. Theuser interface 1900 is therefore integrated with a route planningfeature as discussed above, in connection with display of difficulty anddistance information for a particular route, and is also used to providefeedback to a trail club or other riders regarding a route, as discussedabove in connection with FIG. 6.

In the embodiment shown, the user interface 1900 includes a trail ratingsection 1902 in which the user includes trail ratings regarding thetrail conditions, difficulty, and scenery of the trail, and views anaggregate rating of other riders on that trail. The user interface 1900also includes a trail club region 1904 in which the name of the trailclub managing the trail is shown, as well as options 1906 for the riderto donate to the trail club in varying amounts, as well as on a one-timeor repeated basis.

FIG. 20 illustrates an example user interface 2000 used for integratingsocial media features into a trail rider system for use by a user orrecreational vehicle rider. The user interface 2000 includes a check-inoption 2002, which allows the user to “check in” to a particular trialor point of interest, analogous to many other location-based socialnetworking systems currently available (e.g., Foursquare, Facebook,Google+, etc.). In accordance with the present disclosure, it isunderstood that various other features of such a system, such as“mayorships” or various locations, as well as including arecommendations system as part of the trail feedback, could be includedas well.

A community option 2004 allows the user to view a group of users in thearea, or on the trail, at a particular time, as well as recent activityof the users to which that user is connected (e.g., by using the“follow” option 1708 discussed above). Additionally, a safety option2006 allows for display of safety-related information regarding the rideor operation of a particular recreational vehicle, or features that maybe specific to the trail that is being ridden. Additionally, a rewardsoption 2008 is included, and is used by businesses or other points ofinterest to reward repeated visits or “check-ins” to that business as apoint of interest, or includes incentives that the business wishes toprovide to recreational vehicle riders to encourage them to visit thepoint of interest.

FIGS. 21-22 illustrates user interfaces 2100, 2200, respectively, thatdisplay information that includes integrated vehicle information, suchas some of the types of information available from a vehicle ECU, asdiscussed above in connection with FIGS. 4-5. In the embodiment shown inFIG. 21, a user interface 2100 includes a speedometer 2102, as well asgauges 2104 a-c that display acceleration, power, and torque,respectively. It is understood that other types of gauges, and otherdata, could be included in the display as well. Additional gauge data isdiscussed below. In FIG. 22, a fuel user interface 2200 is displayedthat includes a fuel profile 2202. The fuel profile includes a currentfuel consumption 2204, an average fuel consumption 2206, as well as afuel level 2208 and a range 2210 based on the expected fuel consumptionfor the remainder of the planned route. Additionally, a fuel flow gauge2212, illustrating a rate of fuel flow to the engine, is provided.

In both FIG. 21 and FIG. 22, options are included that allow fornavigation among the available vehicle data. For example, in theembodiments shown, user interfaces 2100, 2200 include a speed option2120 that causes display of the user interface 2100, as well as a fueloptions 2122 that causes display of the user interface 2200. Additionaloptions cause display of other displays; in the example shown, a routeoption 2124 returns the user to the route planning and tracking userinterfaces of FIGS. 7-18, while an engine option 2126 displaysadditional engine parameters to the user, such as the listing ofparameters discussed above as available from the ECU and vehicle 110 ofFIGS. 4-5. Additional menu options are accessible via a “more” option2128 (shown as ellipses).

Referring now to FIGS. 23-24, methods of facilitating usage of arecreational vehicle are discussed, according to example embodiments ofthe present disclosure, including methods for planning and travelingvarious recreational vehicle routes (including off-road routes), as wellas for integrating route planning and vehicle data into a comprehensivedisplay to improve the rider experience.

In the embodiment shown in FIG. 23, a method 2300 is generallyinstantiated with receipt of trail data, for example from a trail dataaggregator or from a plurality of trail clubs (step 2302). Based on thattrail data, one or more users of an application or web interface thenrequest route data, to search for or automatically generate a route thatthe user wishes to traverse (step 2304). This includes, for example,parameters entered by the user, such as a trail difficulty, travel time,specific points of interest or waypoints to be visited, or otheroptions. The mobile application 300 and/or server 102 generates andcauses display of one or more route options based on the parametersprovided by the user (step 2306). Upon display of the one or moreroutes, a user selects a route that he/she wishes to travel (step 2308).

Once the user has selected a desired route, a map illustrating the routeis generated, as illustrated in the user interfaces of FIGS. 7-18,generally (step 2310). The map is selected to display additional optionsrelating to that route, such as points of interest (as in FIG. 10),hazards (as in FIGS. 14-15), buddies located along the route (as in FIG.16), weather information (as in FIG. 18), or other types of information(step 2312). In the embodiment shown, the map displays a currentlocation of the user on that user's display (step 2314), and optionallypublishes that information to other users for tracking in theirapplications, for example in buddy tracker features of correspondingapplications associated with other riders (step 2316). Once the user hascompleted his/her ride, that user then provides feedback regarding theride, such as by providing commentary regarding the route, includingtext or ratings regarding difficulty or scenery of the trail taken (step2318).

Referring now to FIG. 24, a method 2400 for integrating such user-basedinformation as discussed above with vehicle information is provided. Inthe method 2400, a route selection of a user is received (step 2402),and data from a recreational vehicle is also received, for example fromthe vehicle 108 at a server 102 as seen in FIG. 4, or at a mobile device110, as seen in FIG. 5 (step 2404). A display is provided to the user,such as is seen in FIGS. 21-22, that displays vehicle information to auser in an application that combines vehicle and user information (step2406). Optionally, vehicle information and operational parameters canalso be delivered to the server 102 for other purposes as well, such astransmitting error code or maintenance information (steps 2408 and2410). In response, maintenance or repair information is received eitherat the vehicle 108 or mobile device 110, for presentation to a user(e.g., a person needing to repair his/her vehicle while on the trail)(step 2412).

Another embodiment of the present disclosure is illustrated in FIG. 25.In the embodiment of FIG. 25, a human machine interface (HMI) includes amulti-function gauge 414 having a full color display screen. The gauge414 includes an accessory connector 2010 including USB connector port2012 configured to be connected to a USB drive 2014. USB drive 2014illustratively provides software updates, GPS data, special mappinglayers, or other data to the gauge 414. In addition, the USB drive 2014receives data from the gauge 414 such as for recording route informationand “ride data” as discussed herein.

Accessory connector 2010 further includes a video connector 2016configured to be coupled to a video camera 2018. In addition, accessoryconnector 2010 includes a CAN network connection 2020 and an auxiliaryaudio output connector 2022. The auxiliary output connector 2022 isillustratively connected to an audio output device such as a black boxradio 2024 to provide audible alerts or other information to an operatorthrough one or more speakers 2026.

Gauge 414 also includes standard I/O connectors 2028 including power,ground, eight digital I/O connections, three analog I/O connections anda CAN network connection as illustrated at block 2030. As discussedabove, the gauge 414 is connected to an ECU 402 of the vehicle by a CANinterface 410. The CAN interface 410 may also be coupled to the blackbox radio or other audio device 2024.

The gauge 414 is illustratively connected to the user handheld mobiledevice 110 by a suitable connection, preferably a wireless connectionsuch as a Bluetooth data link 2032, to provide communication between thegauge 414 and the mobile device 110. Therefore, the gauge 414 isconnected to the Internet 116 or other communication network to theplurality of data sources discussed herein through the mobile device110. In an illustrated embodiment, phone call and text information froma mobile phone 110 is displayed on gauge 414 as illustrated at block2034. The information displayed on a display of gauge 414 illustrativelyincludes cell signal strength, call notification, text information, anaddress book, or other information from the mobile phone 110. Userinputs on gauge 414 are used to control functions of the mobile device110. Music can also be played from mobile device 110, through gauge 414,and speakers 2026.

Streaming audio is provided to the mobile device 110 as illustrated atblock 2036. When a black box radio 2024 does not have Bluetoothcapability, the streaming audio data is transmitted from mobile device110 to gauge 414 and then through audio output 2022 to the black boxradio 2024.

A mobile application 38 discussed above with reference to FIGS. 1-24provides information such as map data, route information, locationinformation, or buddy tracking, and other information to the mobiledevice 110. In the embodiment of FIG. 25, the data from mobileapplication 2038 is transferred to the gauge 414 for display. Inputsfrom the gauge 414 are transferred to the mobile device 110 to controlfeatures of the mobile application 2038.

A real time route planning mobile application 2040 is used on mobiledevice 110 to plan and display the route information using inputs ongauge 414. For instance, route planning software from Primordial may beused in application 2040. In addition, a vehicle data recording anddiagnostics application 2042 such as a mobile digital wrench iscontrolled and viewed on the gauge 414 through the mobile device 110.

A GPS module 2044 is also coupled to the gauge 414. The GPS module 2044provides location data to the gauge 414 for the mapping, route planning,or other functions described herein.

Referring now to FIG. 26, in another embodiment of the presentdisclosure, a vehicle 3010 has a suspension located between a pluralityof ground engaging members 3012 and a vehicle frame 3014. The groundengaging members 3012 include wheels, skis, guide tracks, treads or thelike. The suspension typically includes springs 3016 and shock absorbers3018 coupled between the ground engaging members 3012 and the frame3014. The springs 3016 may include, for example, coil springs, leafsprings, air springs or other gas springs. The air or gas springs 3016may be adjustable. See, for example, U.S. Pat. No. 7,950,486incorporated herein by reference. The springs 3016 are often coupledbetween the vehicle frame 3014 and the ground engaging members 3012through an A-arm linkage or other type linkage. Adjustable shockabsorbers 3018 are also coupled between the ground engaging members 3012and the vehicle frame 3014. In an illustrated embodiment, a spring 3016and shock 3018 are located adjacent each of the ground engaging members3012. In an ATV, for example, four springs 3016 and adjustable shocks3018 are provided adjacent each wheel 3012. Some manufacturers offeradjustable springs 3016 in the form of either air springs or hydraulicpreload rings. These adjustable springs 3016 allow the operator toadjust the ride height on the go. However, a majority of ride comfortcomes from the damping provided by shock absorbers 3018.

In an illustrated embodiment, the adjustable shocks 3018 areelectrically controlled shocks for adjusting damping characteristics ofthe shocks 3018. An ECU or other controller 402 provides signals toadjust damping of the shocks 3018 in a continuous or dynamic manner. Theadjustable shocks 3018 are illustratively adjustable to providediffering compression damping, rebound damping or both. Additionaldetails of control of the adjustable damping control system aredescribed in U.S. Application No. 61/723,623, filed on Nov. 7, 2012,owned by the assignee of the present application, which is expresslyincorporated herein by reference.

In an illustrated embodiment of the present disclosure, a gauge 414provides a human machine user interface provided in a location easilyaccessible to the driver operating the vehicle. Preferably, the gauge414 is mounted adjacent the driver's seat on the dashboard or integratedonto a display within the vehicle. Gauge 414 includes user inputsdiscussed below to allow the driver or a passenger to manually adjustshock absorber 3018 damping during operation of the vehicle based onroad conditions that are encountered. The display of gauge 414 displaysinformation related to the shock absorber damping settings.

In the illustrated embodiment of FIG. 26, the ECU 402 also controls anelectronic continuously variable transmission (ECVT) 3024 and anelectronic power steering (EPS) 3025 of the vehicle 3010. In anillustrated embodiment, the mobile device 110 or the gauge 414 is usedto control performance features of the vehicle 3010 including theadjustable shocks 3018, the ECVT 3024, the EPS 3025, or otherelectronically controllable performance functions of the vehicle.

The ECU 402 receives inputs from the gauge 414 or mobile device 110 toadjust the damping characteristics of the adjustable shocks 3018 orcontrol the ECVT 3024 or EPS 3025. The front and rear shock absorbers3018 are independently adjustable to adjust the ride characteristics ofthe vehicle 3010.

A plurality of sensors are also coupled to the ECU 402. For example, aglobal change accelerometer 3025 is coupled adjacent each groundengaging member 3012. The accelerometer 3025 provides an output signalcoupled to ECU 402. The accelerometers 3025 provide an output signalindicating movement of the ground engaging members and the suspensioncomponents 3016 and 3018 as the vehicle traverses different terrain.

Additional sensors may include a vehicle speed sensor 3026, a steeringsensor 3028 and a chassis accelerometer 3030 all having output signalscoupled to the ECU 402. Accelerometer 3030 is illustratively athree-axis accelerometer located on the chassis to provide an indicatingof forces on the vehicle during operation. Additional sensors include abrake sensor 3032, a throttle position sensor 3034, a wheel speed sensor36, and a gear selection sensor 3038. Each of these sensors has anoutput signal coupled to the ECU 402. ECU 402 detects when a vehicle isupside down using accelerometer 3030 and sends a distress signal throughmobile device 110.

In one illustrated embodiment, the gauge 414 is used in a demonstrationmode on a showroom floor. The gauge 414 illustratively receives video orother information through USB port 12, video connection 16, or throughhandheld mobile device 110 to provide videos or other information on thedisplay of gauge 414 for promotional purposes.

In another embodiment of the present invention, the gauge 414facilitates tracking of a vehicle. The gauge 414 receives informationfrom the various sensors shown in FIG. 26 and location data from the GPSinput 2044 to track how the vehicle was driven and where it was driven.This “ride data” is stored locally and retrieved, for example, throughUSB port 12 or the data is sent through the mobile device 110 to aremote location for storage and processing. Additional details ofmonitoring, storing, and replaying ride data are disclosed in U.S.Patent Publication No. 2010/0090797, owned by the assignee of thepresent application, which is expressly incorporated herein byreference.

In one illustrated embodiment, an owner can monitor a fleet of vehiclesto determine a location of each vehicle and how the vehicles have beendriven. In another embodiment, the gauge 414 is used to adjust vehiclesettings, such as the springs 3016 or adjustable shocks 3018 of asuspension system or to adjust an electronic continuously variabletransmission (ECVT) 3024 through the gauge 414. Vehicle settings areillustratively based on an experience level of a driver of the vehicle,a route the vehicle is being driven, or other factors. For instance,different settings of the ECVT 3024, suspension system 3016, 3018 orother systems are provided depending on whether the vehicle is beingoperated on-road, on-trail, or off-trail. In an illustrated embodiment,components of the vehicle 3010 are adjusted automatically based on alocation of the vehicle detected using GPS data.

In another embodiment, the mobile device 110 provides a security deviceor security key for the vehicle through its communication with the gauge414. In an illustrated embodiment, the mobile device 110 includes adriver profile including age and experience level. The gauge 414receives the driver profile information from the mobile device 110 andautomatically sets vehicle settings such as the vehicle suspension,shifting patterns, etc. based upon the driver profile.

In another illustrated embodiment, the gauge 414 receives vehicleinformation from the sensors shown in FIG. 26 and provides a timestampon the vehicle kinematic data received. This “ride data” is linked to avehicle location on the route through the GPS data and a timestamp ofthe time at which the vehicle was at the different locations. Therefore,the vehicle can store all information associated with a ride and theuser can replay the ride after it is over as discussed above.

In another embodiment of the present disclosure, the mobile device 110and gauge 414 to track and manage a vehicle. The mobile application 2038tracks and locates a vehicle. A scheduling system prioritizes andassigns use of the vehicle.

Additional details of an illustrated embodiment of the gauge 414 areshown in FIGS. 27 and 28. The gauge 414 includes a body portion 3040housing a display 3042. A plurality of selection buttons 3044 permit theuser to control various features and functions of the present system asdescribed herein. In an illustrated embodiment, the center button 3046is a menu key button. Buttons 3048 and 3050 provide scroll up and scrolldown functionality. Buttons 3052 and 3054 provide selections for variousitems as discussed below.

One illustrated embodiment of the display screen on gauge 414 is shownin FIGS. 29 and 30. For example, gauge 414 is used to display speed,fuel level, coolant temperature, RPM, gear position, trip/odometer,compass, and turn signal indicators. A display screen includes a topportion 3060 which provides header information. Main section 3062 ofdisplay displays information related to the various parameters discussedabove. Section 3064 displays tell-tale information. As shown in FIG. 30,when menu key button 3046 is pressed, the main menu appears on thedisplay screen 3042 of gauge 414. The user then selects differentscreens for display and control. The tell-tales in section 3064 ofscreen illustratively include an engine fault alerts, a low fuel,coolant temperature/level alert, an oil pressure alert, voltage lowalert, parking brake and high beam indicators.

FIGS. 31-34 illustrate various mounting positions for the gauge 414 ofthe present disclosure. In FIG. 31, the gauge 414 is mounted below anexisting display 3070. FIG. 32 illustrates the gauge 414 mounted on afront dashboard of a utility vehicle. FIG. 33 illustrates the gauge 414mounted within a snowmobile. FIG. 34 illustrates the gauge 414 mountedon an ATV.

The system and method of the present disclosure expands the powersportexperience by allowing vehicle users to plan a ride, experience a rideand then re-live the ride. Before the ride, users plan the route andview simulations based on photos, videos or other route informationdiscussed above. Illustrative simulation modes include:

-   -   Trail riding    -   Exploring globally    -   Race the pros    -   Simulated sound and feel a particular vehicle    -   Gaming, racing with the pros in Snow cross, Motocross, etc.:    -   Links to allow on-line shopping. The user can purchase equipment        and accessories for the user's vehicle on-line.

The system and method of the present disclosure builds a user'sexcitement and anticipation before a ride. The user plans the trip withmap software including snowmobile and ATV trail information. The traildatabase includes pictures of points of interest, linked to the map. Theuser also plans entertainment, music, and information, weather radioetc, and trail boss link to companions. The user simulates all or partof the ride on a PC, or the gauge display, which provides a graphicsimulation of the ride, scenery, trail conditions and obstacles.

The user uses a stored ride plan including route information,entertainment, and information flow by loading the stored plan intovehicle systems such as through USB connector 2012. A digital camera orvideo camera 2018 allows the user to record highlights of the ridelinked to the GPS position. During the ride, the system generates a triplog recording actual route, digital photos or videos. Entertainment, andcommunications are indexed in time and recorded. Sensor readings arealso indexed in time to show performance of the vehicle on the ride.

After the ride, the user relives the experience and shares it withothers. The user brings an electronic log back to the PC basedsimulation so that the experience can be relived and shared with others.Indexed to time the simulation include:

-   -   GPS position    -   Trail conditions    -   Weather    -   Communication as it happens    -   The music or entertainment that was playing    -   Photos and videos taken at points of interest

Cellular phone coverage is often not available at locations whererecreational vehicles travel. A navigation and traffic alert system isprovided for recreational vehicle applications, such as off roadvehicles, ATVs, UTVs, and snowmobiles. The system identifies location,direction, and speed of other similar vehicles on roads, trails and inopen terrain. This allows for buddy tracking, fleet management, andtraffic alerts to similarly equipped vehicles remotely or in organizedride park environments. The illustrated system manages availablecommunications networks based on their availability to provide the bestinformation available:

-   -   a. Vehicle system links to smart phones, GPS, and other devices        through a Bluetooth or other similar communication link to share        information and access local and global information networks.    -   b. The system continuously assesses available networks and        utilizes the best network available to transfer data for vehicle        and remote services use. Examples of links could include        cellular service, satellite communications, Wifi, GMRS radio,        and any other available data service.    -   c. When no other source of vehicle-to-vehicle communication is        available, the system of the present disclosure establishes a        local radio transceiver based network using frequencies such as        GMRS band to share vehicle location, direction, and speed with        similarly equipped vehicles. This allows for group ride buddy        tracking, ride park management, and alerts each vehicle to the        approach of other vehicles and safety hazards. Alternatively, a        fixed base radio transceiver could be used in a ride park like        setting to share data with vehicle transceivers to facilitate 2        way communications. Additional information such as radar weather        or general trail conditions and traffic is relayed to all        vehicles on the network and displayed and/or used as        appropriate.    -   d. When no outside network data is available, including        potentially GPS or other locator data, the system predicts, or        dead reckons locations of the vehicle, obstacles, and other        traffic.    -   e. An illustrated embodiment of the system incorporates a        feature similar to 406 MHz distress transmitters to provide a        call for help when other communications aren't available.

In an additional embodiment of the present invention, the system sets amaximum speed for the vehicle based upon driver experience or a locationof the vehicle on a planned route. In addition, the maximum speed may beset depending upon an operation being performed by the vehicle such asmowing or fertilizing. A fleet owner can set a maximum speed for usersof a fleet of vehicles.

Different components of the vehicle, such as the adjustable shocks 3018,the ECVT 3024, the EPS 3025 or other system components such as anelectronic transmission control may be adjusted on the fly during atrip. For example, street mode, a trail mode, an off-trail mode, a rockcrawling mode, or other modes may be set for particular drivingconditions. These adjustments are automatically made as the vehiclepasses over a route or are selected by user using mobile device 110 orgauge 414. In addition, a fuel saving mode may be set for road or trailuse, while a maximum performance mode may be set for off-trail sectionsof the route. A clutching chart is provided for snowmobiles at differentelevations.

In an illustrated embodiment, detected engine faults are displayed onthe display screen of gauge 414 or mobile device 110. A likely cause ofthe fault and possible corrective actions to be taken on the trail arealso displayed on the gauge 414 or mobile device 110. The integratedmapping system displays dealer locations and additional information suchas phone numbers to provide service, help or parts along the route. Themapping system provides a distance to the nearest dealer from thelocation of the vehicle. In one embodiment, a dealer inventory ischecked to determine whether a particular part is available at aparticular dealer.

As discussed above, the system provides live updates through the mobiledevice 110 to the gauge 414 for weather or road conditions and providesoverlays on the route map. For example, snow conditions, weather alerts,traffic alerts, or avalanche advisories are provided.

The gauge 414 is integrated into the vehicle in certain embodiments. Inother embodiments, the gauge 414 is modular and can be removed from onevehicle, such as a utility vehicle, all terrain vehicle, or snowmobileand placed into another vehicle. Security such as using vehicleidentification numbers is provided to reduce theft of the modular gauge414.

In another embodiment, the mobile device 110 includes a control optionfor remotely starting the vehicle or opening a garage door throughcommunication with the gauge 414. A GPS clock or Smartphone clock isillustratively used to control contrast on a display of gauge 414.

Referring now to FIGS. 1-26 generally, it is recognized that, inaccordance with the mobile application, web application, vehicleinterface, and overall system discussed herein, a number of additionalfeatures may be integrated for both on-vehicle and off-vehicle servicesas well. This can include, for example, identification of preferredservice partners to specific OEMs or trail clubs, as well as integratedadvertising in one or both of the web interface and the mobileinterface. It is understood that, in some cases, advertising will belimited to the web interface or to certain user interface screens due toscreen area limitations regarding a mobile device or gauge display, andto avoid displaying advertising to a user of a mobile device or gaugedisplay while that user is operating a recreational vehicle. In anillustrated embodiment, revenue generated from such advertisements isprovided to trail clubs and to maintenance of the system 100 overall.

Referring now to FIGS. 1-26 overall, embodiments of the disclosure arepracticed in various types of electrical circuits comprising discreteelectronic elements, packaged or integrated electronic chips containinglogic gates, a circuit utilizing a microprocessor, or on a single chipcontaining electronic elements or microprocessors. Embodiments of thedisclosure may also be practiced using other technologies capable ofperforming logical operations such as, for example, AND, OR, and NOT,including but not limited to mechanical, optical, fluidic, and quantumtechnologies. In addition, aspects of the methods described herein canbe practiced within a general purpose computer or in any other circuitsor systems.

Embodiments of the present disclosure are implemented as a computerprocess (method), a computing system, or as an article of manufacture,such as a computer program product or computer readable media. Thecomputer program product may be a computer storage media readable by acomputer system and encoding a computer program of instructions forexecuting a computer process. Accordingly, embodiments of the presentdisclosure may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.). In other words,embodiments of the present disclosure may take the form of a computerprogram product on a computer-usable or computer-readable storage mediumhaving computer-usable or computer-readable program code embodied in themedium for use by or in connection with an instruction execution system.A computer-usable or computer-readable medium includes any medium thatincludes media capable of containing or storing the program for use byor in connection with the instruction execution system, apparatus, ordevice.

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the disclosure. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While certain embodiments of the disclosure have been described, otherembodiments may exist. Furthermore, although embodiments of the presentdisclosure have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from theoverall concept of the present disclosure.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

What is claimed is:
 1. A method of facilitating usage of a recreationalvehicle, the method comprising: receiving, from users affiliated with aplurality of authorized groups, trail data, trail condition information,and points-of-interest information from areas affiliated with theauthorized groups, respectively; receiving a request from a user deviceto define a planned off-road route in one or more of the areas;generating a map associated with the planned off-road route, the mapincluding trail condition information and points-of-interest informationreceived; receiving location information from a communications device ata location of a recreational vehicle operated by the user during travelalong the planned off-road route; publishing the location information toone or more other users based on permissions set by the user; andreceiving user feedback information associated with the planned off-roadroute from the user.
 2. The method of claim 1, wherein receipt of thetrail data, trail condition information, and points-of-interestinformation in an area is limited to users affiliated with theauthorized group associated with that area.
 3. The method of claim 1,further comprising integrating weather information from a weather datasource with the trail condition information and points-of-interestinformation in the map generated for the user.
 4. The method of claim 1,further comprising aggregating a plurality of user perspectivephotographs along the planned off-road route, thereby allowingsequential playback of the user perspective photographs.
 5. The methodof claim 1, wherein the communications device comprises a communicationsinterface integrated into the recreational vehicle.
 6. The method ofclaim 1, wherein the communications device comprises a mobiletelecommunications device.
 7. The method of claim 6, wherein the userdevice comprises the mobile telecommunications device.
 8. An applicationembodied on a computer-readable medium, the application executable on acomputing device and including program instructions that, when executed,are configured to cause the computing device to: receive user inputrequesting an off-road route, the user input including one or more rideparameters; define an off-road route based at least in part on the oneor more ride parameters and trail condition data received from one ormore third-party sources; present the off-road route to the user via amap display, wherein presenting the off-road route to the user includespresenting a plurality of route variations to the user, the routevariations including display of one or more ride parameters of the routevariations compared to the off-road route; and receive user selection ofa desired off-road route for traversal.
 9. The application of claim 8,wherein the application comprises a mobile application executable on amobile device.
 10. The application of claim 8, wherein the applicationis executable within a web browser of a computing device.
 11. Theapplication of claim 8, wherein the one or more ride parameters areselected from a group of ride parameters comprising: preferred routedistance; route travel time; nearby points of interest; skill level of arider; and type of off-road vehicle.
 12. The application of claim 8,wherein the one or more third party sources include governmentalorganizations, rider clubs, weather data providers, and other users. 13.The application of claim 8, further comprising presenting a plurality ofdifferent, selectable off-road routes to the user on the map display.14. The application of claim 13, further comprising presenting to theuser an indication of routes traversed by one or more third-partyriders.
 15. The application of claim 14, wherein the indication includesa review of the routes by the one or more third party riders.
 16. Theapplication of claim 8, further comprising, upon receiving userselection of the desired off-road route, providing directions to theuser to follow the desired off-road route.
 17. The application of claim16, further comprising presenting to the user on the map display one ormore points of interest to the user.
 18. The application of claim 16,wherein the plurality of route variations are displayed to the userprior to traversal of the desired off-road route by the user.
 19. Theapplication of claim 16, further comprising, during traversal of thedesired off-road route, generating revised directions for the user upondetermination that the user has departed from the desired off-roadroute.
 20. The application of claim 19, wherein the revised directionsaccount for trail conditions of trails followed using the reviseddirections.
 21. The application of claim 16, further comprisingpresenting to the user a current location of one or more preselectedriders located along the desired off-road route.
 22. The application ofclaim 8, further comprising receiving feedback from the user regardingthe desired off-road route.